-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation of Process to Upgrade AMI for AWS Deployment #7680
Conversation
✅ Deploy Preview for chef-automate ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
For Disaster Recovery or AMI upgarde, while running the restore in secondary cluster which is in different region follow the steps given below. | ||
|
||
- First, Take the bakup in Secondary Cluster | ||
- Then make a curl request `curl -XGET https://localhost:9200/_snapshot?pretty -u admin:admin -k` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This CURL is only supported in the OpenSearch node. Make sure to mention that, or add the endpoint to make same request from Automate Node
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
- First, Take the bakup in Secondary Cluster | ||
- Then make a curl request `curl -XGET https://localhost:9200/_snapshot?pretty -u admin:admin -k` | ||
- check the curl request response if the region is not matching with the primary cluster follow the below steps: | ||
1. Modify the region in fe nodes by patching the below configs with command, `chef-automate config patch <file-name>.toml --fe` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Modify the region in fe nodes by patching the below configs with command, `chef-automate config patch <file-name>.toml --fe` | |
1. Modify the region in the FrontEnd nodes by patching the below configs with command, `chef-automate config patch <file-name>.toml --fe` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
components/docs-chef-io/content/automate/ha_upgrade_introduction.md
Outdated
Show resolved
Hide resolved
|
||
{{< note >}} | ||
|
||
The AWS deployment should be configured with S3. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add more details to this note.
- Which S3 bucket should be configured to the new (upgraded) cluster setup
- Now with MADROX-427, user can directly mention existing bucket name in config.toml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
||
### Steps to set up the AMI Upgraded Cluster | ||
|
||
1. Deploy the Primary cluster following the deployment instructions by [clicking here](/automate/ha_aws_deploy_steps/#deployment). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The assumption here is the user will already have a Primary setup (in case of an AMI upgrade). Do we need to mention Step 1?
- Should we use the terminology
Primary/Secondary cluster
, or can we call this something else ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Discussed ,used Primary and New cluster
- Copy `bootstrap.abb` to all Automate and Chef Infra frontend nodes in the Secondary cluster. | ||
|
||
|
||
1. On New AMI upgraded Cluster |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Either we can use New Cluster with upgraded AMI
or Secondary Cluster(?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
chef-automate backup list | ||
``` | ||
|
||
-On Secondary Cluster Trigger restore command `chef-automate backup restore` on one of the Chef Automate nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-On Secondary Cluster Trigger restore command `chef-automate backup restore` on one of the Chef Automate nodes. | |
- On Secondary Cluster Trigger restore command `chef-automate backup restore` on one of the Chef Automate nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
||
-On Secondary Cluster Trigger restore command `chef-automate backup restore` on one of the Chef Automate nodes. | ||
|
||
- To run the restore command, you need the airgap bundle. Get the Automate HA airgap bundle from the location `/var/tmp/` in Automate instance. For example: `frontend-4.x.y.aib`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Below this line, the Preview link is showing as code snippets for all the descriptions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
||
### Switch to New Upgraded Cluster | ||
|
||
Steps to switch to the New cluster are as follows: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Include steps to re-configure user's DNS to new set of Loadbalances created in the New cluster with upgraded AMIs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
||
In the above approach, there will be two identical clusters | ||
|
||
- Primary Cluster (or Production Cluster) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Primary Cluster (or Production Cluster) | |
- Primary Cluster |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
b073b50
to
aeecb4f
Compare
f451a8b
to
5cdab19
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do the change, other than that ..doc is fine
5cdab19
to
c0fadba
Compare
All the changes are done now. |
components/docs-chef-io/content/automate/ha_upgrade_introduction.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
c0fadba
to
d30979f
Compare
chef-automate backup create --no-progress > /var/log/automate-backups.log | ||
``` | ||
|
||
- Create a bootstrap bundle; this bundle captures any local credentials or secrets that aren't persisted to the database. To create the bootstrap bundle, run the following command in one of the Automate nodes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Create a bootstrap bundle; this bundle captures any local credentials or secrets that aren't persisted to the database. To create the bootstrap bundle, run the following command in one of the Automate nodes: | |
- Create a bootstrap bundle, this bundle captures any local credentials or secrets that aren't persisted in the database. To create the bootstrap bundle, run the following command in one of the Automate nodes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed The Doc Changes.
|
||
- On New Cluster Trigger restore command from bastion. | ||
|
||
- To run the restore command, you need to add the OpenSearch credentials to the applied config. If using Chef Managed OpenSearch,we need to have automate config.Run the below command in the Chef-Automate node to get the applied config into `current_config.toml`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- To run the restore command, you need to add the OpenSearch credentials to the applied config. If using Chef Managed OpenSearch,we need to have automate config.Run the below command in the Chef-Automate node to get the applied config into `current_config.toml`: | |
- For Chef Managed OpenSearch follow the below steps: |
|
||
- Once the restore is successful ,you can destroy the Primary Cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Once the restore is successful ,you can destroy the Primary Cluster. | |
- Once the restore is successful you can destroy the Primary Cluster. |
|
||
``` | ||
|
||
- If you want to reuse the same custom domain used previously, then make sure to update the DNS entry to the Load-Balancer FQDN of the New cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- If you want to reuse the same custom domain used previously, then make sure to update the DNS entry to the Load-Balancer FQDN of the New cluster. | |
- If you want to reuse the same custom domain used previously, update your DNS record to point to the Load-Balancer of the new cluster. |
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
34c15b8
to
935a029
Compare
Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
Kudos, SonarCloud Quality Gate passed! |
* Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> * Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> * Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> * Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> * Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> * Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> * Documentation for AMI upgrade Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com> Signed-off-by: Tejaswi Bondila <bondila.venkatatejaswi@progress.com>
🔩 Description: What code changed, and why?
Created a Docs Page where the Process to Upgrade AMI for AWS Deployment is shown with Backup and Restore method
⛓️ Related Resources
https://chefio.atlassian.net/browse/MADROX-421
👍 Definition of Done
Documentation where the Process to Upgrade AMI for AWS Deployment via Backup and Restore method.
👟 How to Build and Test the Change
✅ Checklist
All PRs must tick these:
With occasional exceptions, all PRs from Progress employees must tick these:
make spell
in any component directory)All PRs from Progress employees should tick these if appropriate:
Please add a note next to any checkbox above if you are NOT ticking it.
📷 Screenshots, if applicable